Also I cleaned up a build queue on TC a little bit removing builds
which cannot make any progress more than 10 hours. Please check your
recent builds.

Most of them was ZooKeeper (Discovery) 3 [1]. It claims that there is
no compatible agents? Could not we run it on any Linux agent?

Also it seems that there is a compatible agent trouble for a GCE [2]
build. Seems it need a special file on an agent

Caused by: java.io.FileNotFoundException:
/home/teamcity/test_keys/gridgain-gce-key.p12 (No such file or
directory)

[1] 
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ZooKeeperDiscovery3&tab=compatibilityList&branch_IgniteTests24Java8=%3Cdefault%3E
[2] 
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Gce&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv

сб, 27 апр. 2019 г. в 07:21, Павлухин Иван <vololo...@gmail.com>:
>
> Igniters,
>
> Indeed it seems that an incident yesterday was caused by Russian
> characters in commit details. I think that following could be done:
> 1. File a bug against TC.
> 2. Do not use Russian characters in git user info, commit messages and
> other commit details.
>
> сб, 27 апр. 2019 г. в 07:20, Павлухин Иван <vololo...@gmail.com>:
> >
> > Igniters,
> >
> > Indeed it seems that an incident yesterday was caused by Russian
> > characters in commit details. I think that following could be done:
> > 1. File a bug against TC.
> > 2. Do not use Russian characters in git user info, commit messages and
> > other commit details.
> >
> > пт, 26 апр. 2019 г. в 10:19, Дмитрий Сорокин <sbt.sorokin....@gmail.com>:
> > >
> > > Hi Ivan!
> > >
> > > Thanks for investigation!
> > > I decided to try second your proposal first, and force pushed the 
> > > squashed commits just now. Let’s look whether it helped or not.
> > >
> > > пт, 26 апр. 2019 г. в 8:57, Павлухин Иван <vololo...@gmail.com>:
> > >>
> > >> I digged a little bit deeper into causes of the VCS problem reported
> > >> by TC. It looks like Russian characters in commit details (an author
> > >> name here) drive TC crazy. Still not sure that it is the root cause
> > >> (quite weird if so).
> > >>
> > >> I found a PR with problematic commits [1]. Dmitrii Ryabov, Dmitriy
> > >> Sorokin and Mikhail Petrov commited to that PR. Guys could you please
> > >> close the PR in order to check that it makes TC mad? It seems that
> > >> closing PR makes no harm because it can be easily reopened after. Or,
> > >> for example squash commits and force push to PR avoiding Russian
> > >> characters.
> > >>
> > >> Need your assistance here.
> > >>
> > >> [1] https://github.com/apache/ignite/pull/6223/commits
> > >>
> > >> пт, 26 апр. 2019 г. в 06:10, Павлухин Иван <vololo...@gmail.com>:
> > >> >
> > >> > Hi Igniters,
> > >> >
> > >> > Right now I am observing that many builds cannot make progress for
> > >> > many hours so far. TC shows that the majority of agents is free [1].
> > >> > But new builds seems fail to start.
> > >> >
> > >> > Does anyone know what is it and how to resolve it? Perhaps simple
> > >> > reboot can help here. Also new codestyle check is a recent change and
> > >> > might be somehow related.
> > >> >
> > >> > Also I see problem with git checkout in some logs:
> > >> > [13:45:12] Collecting changes in 1 VCS root (7s)
> > >> > [13:45:12] [Collecting changes in 1 VCS root] VCS Root details
> > >> > [13:45:18] [Collecting changes in 1 VCS root] Compute revision for
> > >> > 'GitHub [apache/ignite]'
> > >> > [14:36:57] The build is removed from the queue to be prepared for the 
> > >> > start
> > >> > [14:36:57] Starting the build on the agent aitc-lin12:06
> > >> > [14:36:58] Clearing temporary directory: /opt/buildagent/temp/buildTmp
> > >> > [14:36:58] Publishing internal artifacts
> > >> > [14:36:58] Clean build enabled: removing old files from
> > >> > /opt/buildagent/work/69588afcb2ab3382
> > >> > [14:36:58] Checkout directory: /opt/buildagent/work/69588afcb2ab3382
> > >> > [14:36:58] Updating sources: server side checkout (running for 
> > >> > 15h:17m:37s)
> > >> > [14:36:58] [Updating sources] Building clean patch for VCS root:
> > >> > GitHub [apache/ignite]
> > >> > [14:39:20] [Updating sources] Failed to build patch for build #11255
> > >> > {build id=3698721, buildTypeId=IgniteTests24Java8_CacheFailover2}, VCS
> > >> > root: "GitHub [apache/ignite]" {instance id=296, parent internal
> > >> > id=77, parent id=GitHubApacheIgnite, description:
> > >> > "https://github.com/apache/ignite.git#refs/heads/master"}, due to
> > >> > error: Patch building failed:
> > >> > org.apache.catalina.connector.ClientAbortException:
> > >> > java.net.SocketTimeoutException
> > >> > [14:39:20] [Updating sources] Transferring repository sources: 36.93
> > >> > MB so far...
> > >> > [02:40:02] [Updating sources] Transferring repository sources: 36.95
> > >> > MB so far...
> > >> >
> > >> > And a reported problem in "Overview" tab:
> > >> > Error collecting changes for VCS repository '"GitHub [apache/ignite]"
> > >> > {instance id=296, parent internal id=77, parent id=GitHubApacheIgnite,
> > >> > description: "https://github.com/apache/ignite.git#refs/heads/master"}'
> > >> > jetbrains.buildServer.serverSide.db.MySQL.MySqlIncorrectStringValueException:
> > >> > Incorrect string value: '\xD0\xB4\xD0\xBC\xD0\xB8...' for column
> > >> > 'user_name' at row 1 while performing SQL query: SQL DML: insert into
> > >> > vcs_history (modification_id, user_name, description, change_date,
> > >> > vcs_root_id, version, display_version, changes_count, register_date)
> > >> > values (?, ?, ?, ?, ?, ?, ?, ?, ?) | PARAMETERS: 882649, "дмитрий
> > >> > рябов <somefire...@gmail.com>", "fix warming up throttle test\n",
> > >> > 1551457143000, 296, "06127b70b2060dade9bd652abc71f2b949508245",
> > >> > "06127b70b2060dade9bd652abc71f2b949508245", 1, 1556247859429:
> > >> > java.sql.SQLException: Incorrect string value:
> > >> > '\xD0\xB4\xD0\xBC\xD0\xB8...' for column 'user_name' at row 1
> > >> >
> > >> > [1] 
> > >> > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&tab=buildTypeBranches
> > >> >
> > >> > --
> > >> > Best regards,
> > >> > Ivan Pavlukhin
> > >>
> > >>
> > >>
> > >> --
> > >> Best regards,
> > >> Ivan Pavlukhin
> >
> >
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
>
>
>
> --
> Best regards,
> Ivan Pavlukhin



-- 
Best regards,
Ivan Pavlukhin

Reply via email to