Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notify inactive workers when there's a lot of work available #690

Open
shosti opened this issue Oct 7, 2016 · 16 comments
Open

Notify inactive workers when there's a lot of work available #690

shosti opened this issue Oct 7, 2016 · 16 comments

Comments

@shosti
Copy link
Contributor

shosti commented Oct 7, 2016

It would be nice if the extension could optionally notify inactive workers when there's a lot of work, so they might consider connecting. Shouldn't be too hard to do...

@rainforestapp/tester-product sound sane?

@VeryDisappointedTester
Copy link

VeryDisappointedTester commented Oct 7, 2016

That would mean even less work for the testers that are active 10+ hours. Only fair distribution would be one based on testers stats and their activity.

@hunt40
Copy link

hunt40 commented Oct 7, 2016

also lets pointed this fact there is a lot of testers then work,if people inactive that means they are busy or not available to do tests

@VeryDisappointedTester
Copy link

I feel like i'm in the Twilight Zone episode for the last 4-5 weeks.
Every single company in the world would reward workers that are active all day and do their job well.
But instead you keep pushing them away and want to help workers that are satisfied with 1-5 hits a day.
It's like you are reading the manual "What must NOT be done if you want to run a company"

@shosti
Copy link
Contributor Author

shosti commented Oct 8, 2016

2 points:

  1. This would be strictly optional, so people who wanted to be left alone could turn it off
  2. This would only activate if there are more jobs than active testers (i.e. there's work for everyone)

@JrRandy
Copy link

JrRandy commented Oct 8, 2016

Lets get all the errors fixed before worrying about bringing even more people online to cause more errors, and make testing more painful.

@richardfuca
Copy link
Contributor

Yeah I'd say no to this feature request, back in the day of polling I saw
"There are no virtual machines available" errors a lot.
When we have more tests AND more VM's than users then maybe add it in

On 7 October 2016 at 17:57, JrRandy [email protected] wrote:

Lets get all the errors fixed before worrying about bringing even more
people online to cause more errors, and make testing more painful.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#690 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJs-6S0-33rgMWdNSSrM2DSu0-wpE3qGks5qxup-gaJpZM4KRiHQ
.

@VeryDisappointedTester
Copy link

In the last 2-3 hours i've earned more than i earned entire day before that. If u take that away then nothing is left.
There is never enough work. Just keep sending hits.

As people above me said there are a lot of problems with hits. Last few hours almost every hit was very slow. I can't imagine what would be if there were ... lets say another 500+ testers.

@MarinaCec
Copy link

The extension already has noise to warn, who is inactive because is busy or because they don't want to test

@cookin2
Copy link

cookin2 commented Oct 8, 2016

He clearly said: "This would only activate if there are more jobs than active testers (i.e. there's work for everyone)"
He's a forward thinker! Customers would get their runs completed fast and any workers available would be offered the work.

@VeryDisappointedTester
Copy link

This practically means that we will never again get two hits in a row. Every time when there are more hits that testers RF will invite inactive people. After a month with this way you will loose all testers that were active all day long. Quality of results will decline. Just watch and see. When you realise what did you done it will be too late.
Most of the people who are active like 1-2 hours a day dont really care that much about stats.. It is just some thing that brings some minor income.
You have 10000 active testers in the last 24 hours. How many of them are watching AMA or reporting problems? Few hundred at best. Just think about that.

@katiakoroliova
Copy link

I'm online 16h doing rainforest tests, it would be unfair to people like me

@VeryDisappointedTester
Copy link

I wolud ask all testers to think about something.
How many times did you report obvious bug but your bug count did not go up?
How many times every day? How many times in a month?
We all know that there are a lot of testers that dont care. Call them YES workers if you want.
What will happen if they become vast majority of testers?
What result will client get in 10 minutes?

@Electroglitch
Copy link

So many 👎 What is this YouTube? 😆
Joking aside , let's not get ahead of ourselves, first iron out all these errors and hope there will be more available work than available testers... 👍

@cookin2
Copy link

cookin2 commented Oct 8, 2016

@VeryDisappointedTester You've made some very good points that I hadn't thought of, thank you :)

@Dolazim
Copy link

Dolazim commented Oct 8, 2016

Can you add pop up when hit is open we click on him and sound will be stop?

@rainforestapp rainforestapp locked and limited conversation to collaborators Oct 8, 2016
@rainforestapp rainforestapp unlocked this conversation Oct 8, 2016
@rainforestapp rainforestapp locked and limited conversation to collaborators Oct 8, 2016
@shosti
Copy link
Contributor Author

shosti commented Oct 8, 2016

Locking thread for now because it's veered way off topic.

I think y'all are vastly overestimating the effect this would have--it's just a convenience feature for people who want it. (I know we've had requests for this sort of thing before. If anyone has an alternative suggestion that would serve the same purpose, please open up a new issue.)

Also, working on this does not mean "not working on VM issues"--VM reliability is a big and ongoing project (handled by a different team).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

10 participants