hazaar/hazaar-warlock
1
0
Fork 0
Code Issues Pull requests 2 Projects Releases 4 Packages Wiki Activity Actions

Exec limit is not working #45

New issue
Closed
opened 2019-04-11 05:48:33 +00:00 by jamie · 5 comments
jamie commented 2019-04-11 05:48:33 +00:00 (Migrated from git.hazaar.io)
Copy link

I noticed this during testing of another issue.

I have set the exec limit to 1, and then scheduled about 50 jobs that did nothing but output something to the log. Warlock tried to execute all 50 at the same time. Most of them failed because the process ran out of sockets because Windows sucks like that, but they re-executed later just fine, although all at once.

I noticed this during testing of another issue. I have set the exec limit to 1, and then scheduled about 50 jobs that did nothing but output something to the log. Warlock tried to execute all 50 at the same time. Most of them failed because the process ran out of sockets because Windows sucks like that, but they re-executed later just fine, although all at once.
jamie commented 2019-04-11 05:50:25 +00:00 (Migrated from git.hazaar.io)
Copy link

marked this issue as related to #44

marked this issue as related to #44
jamie commented 2019-04-11 05:52:02 +00:00 (Migrated from git.hazaar.io)
Copy link

It would appear that this limit has not actually been implemented. Either that or somewhere along the lines it got removed (which I doubt).

It would appear that this limit has not actually been implemented. Either that or somewhere along the lines it got removed (which I doubt).
jamie commented 2019-04-11 05:58:22 +00:00 (Migrated from git.hazaar.io)
Copy link

Looks like it WAS actually removed accidentally when the server was re-designed in 8082e93b.

Looks like it WAS actually removed accidentally when the server was re-designed in 8082e93b.
jamie commented 2019-04-12 00:19:46 +00:00 (Migrated from git.hazaar.io)
Copy link

closed via commit 8f55272c9a

closed via commit 8f55272c9ac1c7da2b9ce789b160d2e57c9a8c4a
jamie commented 2020-04-14 23:30:32 +00:00 (Migrated from git.hazaar.io)
Copy link

mentioned in commit 8f55272c9a

mentioned in commit 8f55272c9ac1c7da2b9ce789b160d2e57c9a8c4a
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
3.0-develop
58-restful-triggers
2.2-stable
2-warlock-to-warlock-communication
release-2.2.3
release-2.2.2
release-2.2.1
release-2.2.0
release-2.1.5
release-2.1.4
release-2.1.3
release-2.1.2
release-2.1.1
release-2.1.0
release-2.0.2
release-2.0.1
release-2.0.0
release-1.2.6
release-1.2.5
release-1.2.4
release-1.2.3
release-1.2.2
release-1.2.1
release-1.2.0
release-1.1.9
release-1.1.8
release-1.1.7
release-1.1.6
release-1.1.5
release-1.1.4
release-1.1.3
release-1.1.2
release-1.1.1
release-1.1.0
release-1.0.6
release-1.0.5
release-1.0.4
release-1.0.3
release-1.0.2
release-1.0.1
release-1.0.0
release-0.4.0
release-0.3.0
release-0.2.0
release-0.1.0
Labels
Clear labels   
bug

   
confirmed

   
critical

   
discussion

   
documentation

   
Doing

   
enhancement

   
suggestion

   
support

   
To Do
No labels
bug
confirmed
critical
discussion
documentation
Doing
enhancement
suggestion
support
To Do
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-warlock#45
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?