search

brackets-archive / bracketsIssues

Archive of issues in brackets.
0 stars 0 forks source link

[CLOSED] Brackets build jobs colliding, causing failures in Brackets_Build_All #5574

Open core-ai-bot opened 3 years ago

core-ai-bot commented 3 years ago

Issue by jasonsanjose Tuesday Nov 26, 2013 at 00:13 GMT Originally opened as https://github.com/adobe/brackets/issues/6108

Recent failures in the Brackets_Build_All job (see build 499) are due to long running unit test jobs from the prior run. This happens because the build and the 3 test jobs share the same workspace. This happens more frequently on the win8 jenkins node than on the other nodes.

Assigning high priority, sprint 35.

core-ai-bot commented 3 years ago

Comment by peterflynn Tuesday Nov 26, 2013 at 00:53 GMT

@jasonsanjose Are unit tests suddenly taking much longer to run than before? (Does Jenkins capture the length of the job run so we can compare against previous weeks?) We should still fix the race cond here, of course, but if times just went up dramatically it may also be a hint of a new performance or memory-usage regression...

core-ai-bot commented 3 years ago

Comment by jasonsanjose Tuesday Nov 26, 2013 at 17:38 GMT

There's no drastic change in run time for the unit tests, but the build job itself on windows varies pretty wildly from 4:49 to 8:14.

For now, I've scaled back the Git polling from 15 minute intervals to 30 minutes. This should be fine for now, enough to scale back from high to medium priority. Since I was already in the middle of reworking the builds to support a release branch, I'll see if I can work in a fix for this collision.

core-ai-bot commented 3 years ago

Comment by jasonsanjose Tuesday Nov 26, 2013 at 23:40 GMT

Restored 15 minute interval. Found a setting in jenkins to block the Git job if downstream jobs are in progress.