In the time that rain allowed the match to resume, Sri Lanka lost Kaushal Silva in the 16th over as James Anderson caught him leg-before-wicket before rain stopped play for the second time.
Rain headlined the final day but a Sri Lanka protest at a wrongly called no-ball from the previous day was the main highlight.
Flag protest fires up Sri Lanka in Lord's no-ball row
England opener Alex Hales who eventually made 94, was on 58 as he was bowled by Sri Lanka paceman Nuwan Pradeep.
But Australian umpire Rod Tucker had already called a no-ball.
Replays indicated part of Pradeep’s front foot had landed just behind the crease but fielding teams are unable to challenge a no-ball call by an umpire and Hales survived.
Under International Cricket Council (ICC) regulations, incorrect no-ball calls cannot be revoked but umpires can check for a no-ball retrospectively following the fall of a wicket.
Anderson reprimanded over umpire clash
The Sri Lanka flag was draped over the tourists’ dressing-room balcony for some 45 minutes in protest at Tucker’s decision.
Flags traditionally fly above both dressing rooms at Lord’s, and the flag on the balcony was eventually removed at the request of Marylebone Cricket Club, the owners of Lord’s.
“You feel a little down, it is sad,” Sri Lanka Cricket president Thilinga Sumathipala told reporters. “The management on tour is very sad about that decision. It will be reported to the ICC.”
Shearer and Cook head Queen's sporting honours
Several close Decision Review System calls went against Sri Lanka on Sunday and the visitors were not too pleased about it.
“If the decisions are continually happening against you many times then they [the players] will get demoralised,” said Sumathipala. “If they feel it’s only happening to us, that’s sad.”
Published in The Express Tribune, June 14th, 2016.
Like Sports on Facebook, follow @ETribuneSports on Twitter to stay informed and join in the conversation.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ